v0.3.0: add view counts, logs, and list --json - #3

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 29: Update the test:coverage workflow so the CLI is built from current
source before coverage tests run. Prefer adding the existing build command to
the test:coverage script, or update the CLI setup in test/helpers.ts to invoke
the build before executing dist/cli.js.

In `@src/commands/deploy.ts`:
- Around line 198-208: Update the URL identifier selection around urlSlug in the
deploy command so any --update deployment uses opts.update as the stable
identifier, including when result.slug is populated or name lookup returns no
slug. Preserve the existing opts.name preference for new named deployments and
ensure watchTarget/watchSlug use the same stable identifier.

In `@src/commands/logs.ts`:
- Around line 51-57: Update the appended-log read flow around the read loop and
process.stdout.write to use a persistent streaming UTF-8 decoder instead of
decoding each buffer independently. Preserve decoder state across successive
reads, and reset that decoder whenever the truncation or rotation handling at
line 48 resets the file offset.
- Around line 28-29: Update the logs command around readLogTail so it reads
backward through multiple chunks rather than stopping after one 16 KiB chunk.
Continue until the requested lineCount newline delimiters are collected or the
beginning of the file is reached, while preserving the existing tail output
behavior.

In `@src/commands/status.ts`:
- Around line 93-109: Update readLogTail so a chunk without a newline is not
discarded when it contains the file’s final non-empty line; expand the read
window backward until a newline boundary is found, while preserving removal of
the initial partial line. Add a regression test covering a 17 KiB single-line
log and verify the tail remains truthy and is returned by the logs command.

In `@src/server/public.ts`:
- Around line 95-99: Update the public request handler and its response helpers,
including the no-slug path and sendErrorPage, to receive the request method and
suppress response bodies for every HEAD request. Preserve the existing status
codes and headers, but call res.end without content for HEAD while retaining
HTML bodies for GET.

In `@src/server/ws.ts`:
- Around line 47-57: The WebSocket client map currently uses the host-derived
slug instead of the canonical slug, preventing reload broadcasts from reaching
those clients. In the upgrade flow and the corresponding close and error
handlers, use a shared client key of resolved ?? slug when accessing
this.clients, while preserving the existing authentication and connection
behavior.

In `@src/storage/index.ts`:
- Around line 511-518: Update recordHit so repeated page views do not
continually reset the pending persistence deadline: preserve the hit and
timestamp updates, but ensure scheduleFlush retains an existing timer or
otherwise enforces a maximum flush interval. Use the existing scheduleFlush
mechanism and keep only one pending flush so sustained traffic eventually
persists the changes.

In `@test/api.test.ts`:
- Around line 389-397: Update the response Promise in the affected API test so
the `end` listener rejects with the actual status when it is not 200, rather
than throwing an assertion inside the callback; keep parsing and resolving the
JSON for successful responses, then move the status expectation to execute after
awaiting the Promise.

In `@test/cli.test.ts`:
- Around line 360-366: Strengthen the test case around the deploy invocation by
asserting that runCli(["deploy", f, "--protect", "hunter2"], ...) succeeds
before querying deployments. Update the JSON assertion to verify the protected
entry for the slug created by this test rather than accepting any protected
deployment in the shared daemon.home state, while retaining the access-key
non-leak assertion.

In `@test/config.test.ts`:
- Around line 115-118: The afterEach cleanup unconditionally assigns an
undefined HOME value, causing Node to store the literal "undefined". In
test/config.test.ts lines 115-118 and test/api-client.test.ts lines 25-28,
update the HOME restoration to delete process.env.HOME when the captured value
is undefined; otherwise restore the captured value, then retain the existing
fs.rmSync cleanup.

In `@test/global-setup.ts`:
- Line 20: Update the temp-directory name filter in the global setup cleanup
logic to allow digits in the prefix segment, so names such as uptool-api-utf8-*
are swept while retaining the existing uptool- prefix and trailing-hyphen
requirements.

In `@test/helpers.ts`:
- Around line 188-192: Update startDaemon to continuously drain both
child.stdout and child.stderr with data handlers, retaining only a bounded
recent-output buffer. When waitForPort fails or times out, include the buffered
stdout and stderr tail in the startup error while preserving the existing
successful startup behavior.

In `@test/status.test.ts`:
- Around line 414-441: Replace the fixed-delay settle helper in the followLog
tests with a deadline-based waitFor helper that repeatedly checks for the
expected emitted content and times out clearly; update both append and
truncation tests to use it and raise their test timeout as needed. Keep a fixed
short delay for the stop() releases the watcher absence assertion, or use
waitFor with a rejects assertion.

In `@test/storage.test.ts`:
- Around line 771-787: Update the version-ID generation used by ManifestStore
update/version persistence in src/storage/index.ts so consecutive updates within
the same millisecond always receive distinct IDs; when Date.now() matches an
existing newest version, append or increment a deterministic suffix (or
equivalent unique value). Ensure the generated ID is unique before creating the
version directory and adding it to entry.versions, preserving rollback and
pruning behavior without duplicate manifest entries.

In `@test/ws.test.ts`:
- Around line 62-66: Update the cleanup call in the server.close callback to
pass force: true alongside recursive: true when invoking fs.rmSync on tmpDir,
ensuring cleanup remains idempotent and resolve() is reached if the directory
was already removed.

---

Nitpick comments:
In `@test/api.test.ts`:
- Around line 409-413: Update the cleanup in the test’s finally block to remove
tmpDir2 with recursive and force options so an already-absent directory does not
mask the original failure. Also guard bigStore.flushNow() as needed so cleanup
does not write to or recreate the directory before removal.

In `@test/global-setup.ts`:
- Around line 19-29: Update the cleanup loop around readdirSync in the global
teardown to avoid deleting active concurrent-run directories: inspect each
matching entry’s modification time and remove it only when it exceeds the chosen
stale-age threshold. Preserve the existing recursive, forced removal and
best-effort error handling for eligible entries.

In `@test/public.test.ts`:
- Around line 516-522: Remove the stale “Handler throw -> 500, not a dead
daemon” section header from above the “View counting (recordHit)” block; keep
the existing handler-throw test and view-counting section marker aligned with
their respective tests.

In `@test/storage.test.ts`:
- Around line 547-568: Update the base64 size estimation test to exercise the
production estimator used by storage code instead of duplicating its formula
inline. Export and import that estimator from the relevant storage module, then
call it for each padding case while retaining the decoded-length assertions;
alternatively, test store() with max_file_size thresholds immediately above and
below the true decoded size.

In `@test/ws.test.ts`:
- Around line 170-182: Update the timer setup in the heartbeat test around
WsManager construction to fake only setInterval and clearInterval, leaving
setImmediate and other real event-loop APIs available for connectLr() websocket
I/O. Preserve the existing timer advancement and cleanup behavior.